Short message service (sms) communication in wireless networks in the packet switched domain

ABSTRACT

Technology for communicating a short message service (SMS) communication in a packet switched (PS) domain of an evolved packet system (EPS) network. One method comprises receiving, at a core network (CN) control node, a request message from a user equipment (UE) indicating that the UE supports PS based SMS and performs a circuit switched (CS) registration only to receive SMS service via a CS domain; and sending, from the CN control node, an accept message to the UE indicating that SMS over a non-access stratum (NAS) is supported by the CN control node.

RELATED APPLICATIONS

This application claims the benefit of and hereby incorporates byreference U.S. Provisional Patent Application Ser. No. 61/621,939, filedApr. 9, 2012, with an attorney docket number of P44666Z.

BACKGROUND

As the use of mobile wireless devices, such as smart phones and tabletdevices, becomes more ubiquitous, the demands on the limited amount ofradio frequency spectrum used by those devices also increases, resultingin wireless network congestion in the licensed spectrum. In addition,the increased use of high bandwidth applications such as audio and videostreaming can increase demands beyond the capability of the availablespectrum. This is especially true in high density and high use locationssuch as large cities and universities. One projection estimates a growthof 20 times in mobile internet traffic from 2010 to 2015.

Improvements in wireless architectures, hardware design, and processorspeed have significantly increased the efficiency of wireless devices intheir use of the available spectrum. However, certain legacy aspectsfrom previous generations of wireless network specifications continue toreduce the potential efficiency of modern wireless architectures.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the invention will be apparent from thedetailed description which follows, taken in conjunction with theaccompanying drawings, which together illustrate, by way of example,features of the invention; and, wherein:

FIG. 1 illustrates an example of a General Packet Radio Service (GPRS)Logical Architecture when based on the S4, S5, and S8 interfaces;

FIG. 2 illustrates an a Mobility Management Entity (MME) architectureconfigured to provide packet switched (PS) Short Message Service (SMS)communications in accordance with an example;

FIG. 3 illustrates an example of an Attach Request message illustratedin a table format;

FIG. 4 illustrates an EPS mobility management (EMM) message informationelement that includes a new cause message in accordance with an example;

FIG. 5 depicts a flow chart of a method for communicating a shortmessage service (SMS) communications in a packet switched (PS) domain ofan evolved packet system (EPS) network in accordance with an example;

FIG. 6 depicts a flow chart of a method for adapting a wireless networkfor packet switched communication of a short message service message inaccordance with an example; and

FIG. 7 illustrates a mobile wireless device in accordance with anexample.

Reference will now be made to the exemplary embodiments illustrated, andspecific language will be used herein to describe the same. It willnevertheless be understood that no limitation of the scope of theinvention is thereby intended.

DETAILED DESCRIPTION

Before the present invention is disclosed and described, it is to beunderstood that this invention is not limited to the particularstructures, process steps, or materials disclosed herein, but isextended to equivalents thereof as would be recognized by thoseordinarily skilled in the relevant arts. It should also be understoodthat terminology employed herein is used for the purpose of describingparticular embodiments only and is not intended to be limiting.

DEFINITIONS

As used herein, the term “substantially” refers to the complete ornearly complete extent or degree of an action, characteristic, property,state, structure, item, or result. For example, an object that is“substantially” enclosed would mean that the object is either completelyenclosed or nearly completely enclosed. The exact allowable degree ofdeviation from absolute completeness may in some cases depend on thespecific context. However, generally speaking the nearness of completionwill be so as to have the same overall result as if absolute and totalcompletion were obtained. The use of “substantially” is equallyapplicable when used in a negative connotation to refer to the completeor near complete lack of an action, characteristic, property, state,structure, item, or result.

As used herein, the term “Core Network (CN) control node” is a genericterm that refers to either a Mobility Management Entity (MME) or aServing GPRS (General Packet Radio Service) Support Node (SGSN).

As used herein, the term User Equipment (UE) refers to a wireless deviceconfigured to communicate with a Third Generation Partnership Project(3GPP) wireless network.

As used herein, the term mobile station (MS) refers to a wireless deviceconfigured to communicate with a Third Generation Partnership Project(3GPP) wireless network. The terms UE and MS are considered to besynonymous and may be used interchangeably throughout this document,unless otherwise noted.

Additional definitions may be provided in the proceeding paragraphs inthe example embodiments.

Example EMBODIMENTS

An initial overview of technology embodiments is provided below and thenspecific technology embodiments are described in further detail later.This initial summary is intended to aid readers in understanding thetechnology more quickly but is not intended to identify key features oressential features of the technology nor is it intended to limit thescope of the claimed subject matter.

An exponential increase in the amount of wireless data transmission hascreated congestion in wireless networks using licensed spectrum toprovide wireless communication services for wireless devices such assmart phones and tablet devices, to name a few. The congestion isespecially apparent in high density and high use locations such as urbanlocations and universities.

One technique for providing additional bandwidth capacity to wirelessdevices is through the transformation of wireless networks from circuitswitching to packet switching. In circuit switching, wirelesscommunication involves using a limited number of dedicated connectionsthat typically have a constant bit rate and a constant delay between thewireless nodes. These dedicated connections may be open even if no datais being transmitted by a wireless device. This can lead toinefficiencies in the use of radio frequency spectrum.

In contrast with circuit switching, packet switching involves groupingdata that is to be transmitted, regardless of the data's content, type,or structure, into blocks referred to as packets. Packet switchingprovides the ability to deliver variable bit rate data streams over ashared network. Packets can be buffered or queued at network adapters,switches, routers, or other network nodes, thereby enabling packets tobe delivered with variable delay and throughput depending on the trafficload in the network. The use of packet switching improves the ability ofa wireless network to provide a desired Quality of Service (QoS) in awireless network. In addition, the use of packet switching cansignificantly improve the efficiency in which data is transmitted,resulting in lower costs for consumers and more efficient use of thecrowded radio frequency spectrum.

As wireless communication standards have continued to develop, the useof packet switching has become more and more prevalent. However, certainlegacies from earlier standards still remain in even the most modernwireless communication standards. One such legacy is the use of circuitswitching to communicate Short Message Service (SMS) communicationsbetween wireless devices configured to operate with the Third GenerationPartnership Project (3GPP) Long Term Evolution (LTE) specification.

Short Message Service communications, which are typically referred to as“text messaging” is a communications protocol that enables theinterchange of a text message of up to 160 characters in length betweenmobile devices. Messages are sent to a Short Message Service Centre(SMSC) where they can be stored until the destination wireless device isactive. Once the destination wireless device is connected to a wirelessnetwork, the SMS message can be communicated from the SMSC to thewireless device.

Releases 8, 9, 10 and 11 (Stage 2 freeze in September, 2012) of the 3GPPLTE specification still use circuit switching (CS) to provide SMScommunications. The communication of SMS is one of the last vestiges ofCS in the 3GPP network. In order to provide SMS communication using CS,a user equipment (UE) typically has to connect with a Mobile SwitchingCenter (MSC). The MSC provides an interface between the radio system andthe fixed networks. The MSC can perform desired functions in order toprovide CS services to and from the UE. Thus, user equipment (UEs) oftenconnect with an MSC. This connection can result in excessive overhead,as well as the use of unnecessary dedicated wireless connections.

To overcome this limitation, the advent of SMS communication usingpacket switching (PS) in the 3GPP network can be implemented. Theimplementation of PS based SMS can be accomplished in different waysdepending on the age and/or architecture of the wireless network.

Modern 3GPP LTE based networks can implement PS based SMS communicationusing the network's Mobility Management Entity (MME). The MME is thecontrol node that processes the signaling between the UE and the CoreNetwork (CN). The MME can provide Visitor Location Register (VLR)functionality for an Evolved Packet System (EPS). This will be discussedmore fully in the proceeding paragraphs.

Older wireless networks can include an assortment of old and newwireless networking equipment. The wireless networking equipment isoften generally referred to based on the “generation” to which theequipment belongs, according to the equipment's age and capabilities.For example, wireless networking equipment may be designated based onthe “generation” to which the equipment belongs, such as 2G, 2.5G, 3G,or 4G. Networks that include an assortment of different generations caninclude a Serving GPRS (General Packet Radio Service) Support Node(SGSN).

GPRS is a mobile data service extension to the Global System for Mobilecommunications (GSM). GSM is a 2G system. GPRS is often described as a2.5G system. The SGSN acts as the control node, similar to the MME in 4Gsystems. The SGSN is the interface between the radio system and thefixed network for Packet Switched (PS) services. The SGSN can performthe functions to handle packet transmission to and from the UE. The SGSNcan be used to provide PS based SMS, thereby eliminating the need for aUE to connect to an MSC merely for SMS communication in a 2.5G or 3Gwireless network.

A discussion of the SMS in SGSN architecture for SMS services will bedescribed below. Messaging used between the UE and the SGSN to implementthe SMS in SGSN architecture will be provided. A discussion of the SMSin MME architecture will follow.

FIG. 1 provides an example of a GPRS Logical Architecture when based onS4/S5/S8 interfaces. The architecture is described in the 3GPP TechnicalSpecification (TS) 23.060. One example is provided in 3GPP TS 23.060V11.1.0 (2012-03).

A GPRS Support Node (GSN) contains functionality used to support GPRSfunctionality for the GSM/EDGE Radio Access Network (GERAN) and/or theUniversal Terrestrial Radio Access Network (UTRAN). In one Public LandMobile Network (PLMN), there may be more than one GSN.

The SGSN and Gateway GPRS Support Node (GGSN) functionalities may becombined in the same physical node, or they may reside in differentphysical nodes. The SGSN and the GGSN contain Internet Protocol (IP) orother (i.e. Asynchronous Transfer Mode (ATM)) routing functionality. TheSGSN and GGSN may be interconnected with IP routers.

The Gateway GPRS Support Node (GGSN) is the node that is accessed by thepacket data network (PDN) after evaluation of the Packet Data Protocol(PDP) address. The GGSN contains routing information for PS-attachedusers. The routing information is used to tunnel N protocol data units(PDUs) to the UE's current point of attachment, i.e. the Serving GPRSSupport Node. The GGSN may request location information from the HomeLocation Register (HLR) via the optional Gc interface. The GGSN is thefirst point of PDN interconnection with a PLMN supporting GPRS (i.e. theGi reference point is supported by the GGSN). GGSN functionality iscommon for all types of RANs.

The Serving GPRS Support Node (SGSN) is the node that is serving the UE(i.e. mobile station (MS)). The SGSN supports GPRS for A/Gb mode (i.e.the Gb interface is supported by the SGSN) and/or lu-mode (i.e. the luinterface is supported by the SGSN). At PS attach, the SGSN establishesa mobility management context containing information pertaining to e.g.mobility and security for the MS. At PDP Context Activation, the SGSNestablishes a PDP context, to be used for routing purposes, with theGGSN that the subscriber will be using. In lu mode, the SGSN and RNC maybe interconnected with one or more IP routers.

In Gn/Gp mode and when the SGSN and the GGSN are in different PLMNs,they are interconnected via the Gp interface. The Gp interface providesthe functionality of the Gn interface, plus security functionalityrequired for inter-PLMN communication. The security functionality isbased on mutual agreements between operators.

In Gn/Gp mode, the SGSN interworks signaling on the Gn/Gp interface withlu/Gb interface signaling. In S4 mode, the SGSN interworks signaling onthe S4 interface with lu/Gb interface signaling. One SGSN may have someUEs using Gn/Gp mode and other UEs using S4 mode.

The SGSN may send location information to the MSC/VLR via the optionalGs interface. The SGSN may receive paging requests from the MSC/VLR viathe Gs interface.

The SGs interface can connect databases in the VLR and the MME. The SGsis also used to convey some circuit switched related procedures via theMME. The basis for the interworking between a VLR and an MME is theexistence of an SGs association between those entities per UE. The SGsassociation is applicable to UEs which are configured to use CS fallbackand SMS ove SGs, or SMS over SGs only. The SGs association is notapplicable if the subscriber data indicates that the subscription is forpacket switched (PS) communication only. The SGs association is also notapplicable if the Home Subscriber Server (HSS) signals “SMS in MMESupport” capability and the MME determines that SMS service is to beprovided using the SMS in MME feature.

The SGSN interfaces with the GSM-SCF for optional Customized Applicationfor Mobile Enhanced network Logic (CAMEL) control using the Ge referencepoint. Depending on the result from the CAMEL interaction, the sessionand packet data transfer may proceed normally. Otherwise, interactionwith the GSM-SCF continues as described in TS 23.078.

The functionality of the Serving Gateway is defined in 3GPP TS 23.401with the following additions and exceptions: The Serving Gateway canterminate the user plane interface towards the UTRAN when the DirectTunnel feature is in use. The Serving Gateway is the local MobilityAnchor point for the Serving Radio Network Subsystem (SRNS) relocationwhen the Direct Tunnel feature is in use. The Serving Gateway can alsobe the local Mobility Anchor for an inter-SGSN routing area update.

SMS in SGSN Architecture

In accordance with one embodiment of the present invention, the SMS inSGSN can be performed as follows. An indication can be added where theSGSN indicates to the Home Subscriber Server (HSS) in the Attach/RoutingArea Update (RAU) procedures that it offers SMS in SGSN using the Gd.Subscription data information can be added for “PS-and-SMS-only”subscriptions. The SGSN identity can be registered for terminating SMSservices. When this occurs, the HLR, operating on the HSS, can cancelany registered MSC. These operations align the behavior of the HLR/HSSfor SGSN and MME. The handshaking of SMS support between the HSS and theSGSN (in both directions) can be based on existing Teleservice Listparameters in the Gr MAP and S6d Diameter protocols. The Inter-SGSN RAUprocedure can be updated to provide the same support for “SMS in SGSN”as the combined Attach/RAU procedures. A clarification about the“SMS-Supported” indication to the MS can be added in the GPRS AttachProcedure.

The SGSN can indicate that it offers SMS services via the PS domain(i.e. Gd) to the HSS by an indication “SMS in SGSN offered” in thesignaling with the HSS during the Attach/RAU procedure. When thesubscription information indicates “PS and SMS only” the HSS can respondto queries from SMS-GMSCs and SMS routers so that Mobile Terminated (MT)SMS gets routed to serving nodes in the PS domain when SMS via the PSdomain are offered by these serving nodes.

A CS/PS enabled UE that needs only PS domain services and SMS servicesover a Non Access Stratum (NAS) layer indicates this capability as“SMS-only” to the SGSN during combined Attach/RAU procedures, i.e. theincluded CS registration is only requested for obtaining SMS servicesover NAS. Based on the UE provided information (i.e. the SMS-onlyindication to the SGSN) and when the HSS provided subscriptioninformation indicates “SMS in SGSN Support” and the SGSN supports SMSservices over NAS, the SGSN can then determine to not establish anassociation with an MSC when requested by the UE in the combinedAttach/RAU procedures.

The SGSN can forward the capability indicated by the UE as an “SMS-only”indication in the Location Update procedure to the HSS. If the HSS hasan old serving MSC registered, the HSS can cancel the serving MSC for aUE that indicates “SMS-only” and subscribes to SMS services if both theSGSN and the HSS supports SMS in SGSN (i.e. the SGSN has indicated “SMSin SGSN offered” and the HSS supports SMS in SGSN). As only the SGSN isregistered for MT SMS, the HSS can then respond to queries fromSMS-GMSCs and SMS routers so that MT SMS is routed to serving node(s) inthe PS domain.

SMS in MME Architecture

FIG. 2 provides an illustration of an MME architecture configured toprovide PS based SMS services. The MME is in communication with the HSSvia an S6a interface, which is a Diameter based interface that isenhanced with SMS support. A new direct “E” interface exists between theMME and SMS central functions, such as SMS router, SMS-Gateway MobileSwitching Center (GMSC) and SMS-Inter Working Mobile Switching Center(IWMSC). The E interface can be either a MAP or Diameter based protocol.

Mobile Application Part (MAP) is an SS7 protocol which provides anapplication layer for the various nodes in GSM and UMTS mobile corenetworks and GPRS core networks to communicate with each other in orderto provide services to mobile phone users. The Mobile Application Partis the application-layer protocol used to access the Home LocationRegister, Visitor Location Register, Mobile Switching Center, EquipmentIdentity Register, Authentication Centre, Short message service centerand Serving GPRS Support Node (SGSN).

The SGs interface can be used to relay SMS messages between the MME andVLR. The SMS-Switching Center (SC) may be integrated with theSMS-GMSC/SMS_IWMSC. The interface between the HSS and SMS centralfunctions (SMS_IWMSC and SMS-GMSC, SMS-router) can be Diameter or a MAPC interface. There is a Diameter E interface between the MME and SMScentral functions.

The use of the SMS in MME architecture is for SMS services only. Thisfunctionality may not trigger any CS fallback and does not require anSGs. In addition, to provide SMS In MME, the MME can be configured toprovide the following: SMS procedures between the UE and the MME caninclude support for the Short Message Control (SMC) and Short MessageRelay (SMR) functions.

In one embodiment, the MME can be configured to support the combinedEPS/IMSI procedures for “SMS-only” and in these: provide anon-broadcasted Location Area Identity (LAI) that is not associated withany Visitor Location Register (VLR). If needed, the MME can provide areserved TMSI that is configured such that it cannot cause anyambiguities with other TMSIs. For instance, when the UE changes to anarea where it needs to derive SMS services from a GERAN/UTRAN MSC. TheMME can indicate in the Attach/TAU Accept message that the IMSI attachis for “SMS-only”. The MME can notify the HSS that it is capable of SMStransfer without the need of establishing an SGs association with anMSC. The MME can obtain SMS related subscription information.

If the UE performs a combined attach/TAU with “SMS-only” indication, theMME can forward the “SMS-only” indication in the location updateprocedure to the HSS. The HSS can allow an operator to configure asubscription that is limited to only PS services and SMS services. Thislimitation is indicated in the PS subscription data as “PS and SMSonly”.

In order to setup a 3GPP LTE EPS to provide PS based SMS, a UE canindicate its request for SMS services to the MME. This can involvesending a message that the UE only request CS registration to receiveSMS services, but is capable of supporting PS based SMS. One way ofcommunicating this message from the UE to the MME is by altering anAttach Request message. The Attach Request message is defined in 3GPP TS24.301. One example is shown in 3GPP TS 24.301 V11.3.0 (2012-06).

The Attach Request message is sent by the UE to the network in order toperform an attach procedure with the network. An example of an AttachRequest message is illustrated in FIG. 3 in a table format. The tableincludes information including the Information Element Identifier (IEI),the name of the Information Element (IE), the type of IE and a referenceto the IE in the 3GPP TS 24.301, along with the presence, format, andlength of each IE in the Attach Request message.

In accordance with one embodiment, the UE shall include an additional IEin the Attach Request message if the UE requests “SMS only” or if the UEsupports PS based SMS and does CS registration only to receive SMSservice via the CS domain. Several different types of IE can be used tocommunicate this message from the UE to the MME. Five different examplesare provided herein. These examples are not intended to be limiting. Anymeans may be used to communicate this message from the UE to the MME.The examples below are labeled Solution A through Solution E.

Solution A

In this solution, a new IE Additional Update Type is added to the AttachRequest message. The format of the Additional Update Type IE is providedin the proceeding paragraphs.

The purpose of the additional update type IE is to provide additionalinformation about the type of request for a combined attach (i.e. anAttach/RAU procedure) or a combined tracking area updating procedure.The Additional Update Type IE can be coded as shown in Table 1 and Table2.

TABLE 1 Additional Update Type information element

TABLE 2 Additional Update Type information element Additional updatetype value (AUTV) (octet 1) Bit 1 0 No additional information. Ifreceived it shall be interpreted as request for combined attach orcombined tracking area updating. 1 SMS only PS SMS Support (PSSS)(octet 1) Bit 2 0 UE does not support PS based SMS 1 UE supports PSbased SMS and does CS registration only to receive SMS service via CSdomain Bits 4 to 3 of octet 1 are spare and shall be all coded as zero.

As shown in Table 2 above, Bit 2 in octet 1 can be a PS based SMSSupport (PSSS) message. In this example, a Bit value of 0 provides themessage that the UE does not support PS based SMS. A Bit value of 1provides the message that the UE supports PS based SMS and does CSregistration only to receive SMS service via the CS domain. The IEillustrated in Table 1 and 2 can be included in the Attach Requestmessage shown in FIG. 3.

Solution B

In this solution one spare bit of the MS Network Feature Support IE ofthe Attach Request message is used to indicate a UE PS-only capabilityto the network; i.e. that the UE intent to request CS registration onlyfor obtaining SMS services, but is capable of PS based SMS.

In accordance with one embodiment, the MS Network Feature Support IE,which is defined in section 9.9.3.20A of 3GPP TS 24.301 and section10.5.1.15 of 3GPP TS 24.008, can be configured to include a PS based SMSSupport message, as follows. One example of the 3GPP TS 24.008 is TS24.008 V11.3.0 (2012-06).

TABLE 3 MS Network Feature Support information element

TABLE 4 MS Network Feature Support information element Extended periodictimers (octet 1) Bit 1 0 MS does not support the extended periodic timerin this domain 1 MS supports the extended periodic timer in this domainThe relevant extended periodic timer is T3212 for Mobility Management(MM) messages, T3312 for GPRS MM (GMM) messages, and T3412 for EPS MM(EMM) messages. PS based SMS Support (PSSS) (octet 1) Bit 2 0 MS doesnot support PS based SMS 1 MS supports PS based SMS Bit 2 set to 1indicates MS support PS based SMS and CS registration is only to receiveSMS service Bits 4 and 3 of octet 1 are spare and shall be coded aszero.

As illustrated in Tables 3 and 4, Bit 2 in octet 1 can be a PS based SMSSupport (PSSS) message in the MS network feature support IE. In thisexample, a Bit value of 0 provides the message that the MS does notsupport PS based SMS. A Bit value of 1 provides the message that the MSsupports PS based SMS and does CS registration only to receive SMSservice via the CS domain. The IE illustrated in Table 3, 4 can beincluded in the Attach Request message shown in FIG. 3.

Solution C

In this solution, one spare bit of the UE Network Capability IE of theATTACH REQUEST message is used to indicate UE PS-only capability to thenetwork; i.e. the UE's intent to request CS registration only forobtaining SMS based service, but is capable of PS based SMS.

In accordance with one embodiment, the UE Network Capability IE, whichis defined in section 9.9.3.34 of 3GPP TS 24.301, can be configured toinclude a PS based SMS Support message, as follows.

TABLE 5 UE Network Capability information element

TABLE 6 UE Network Capability information element PS based SMS Support(PSSS) (octet 7, bit 7) 0 MS does not support PS based SMS 1 MS supportsPS Based SMS Bit 7 set to 1 indicates MS support PS based SMS and CSregistration is only to receive SMS service All other bits in octet 8 to15 are spare and shall be coded as zero, if the respective octet isincluded in the information element.

As illustrated in Tables 5 and 6, Bit 7 in octet 7 can be a PS based SMSSupport (PSSS) message in the UE Network Capability IE. In this example,a Bit value of 0 provides the message that the MS does not support PSbased SMS. A Bit value of 1 provides the message that the MS supports PSbased SMS and does CS registration only to receive SMS service via theCS domain. The IE illustrated in Table 5 and 6 can be included in theAttach Request message shown in FIG. 3.

Solution D

In this solution one spare bit of EPS Attach Type IE of ATTACH REQUESTis used to indicate UE PS-only capability to the network i.e. the UE'sintent to request CS registration only for obtaining SMS based service,but is capable of PS based SMS.

In accordance with one embodiment, the EPS Attach Type IE, which isdefined in section 9.9.3.11 of 3GPP TS 24.301, can be configured toinclude a PS based SMS Support message, as follows.

TABLE 7 EPS Attach Type information element

TABLE 8 EPS Attach Type information element EPS attach type value(octet 1) Bits 3 2 1 0 0 1 EPS attach 0 1 0 combined EPS/IMSI attach 1 10 EPS emergency attach 1 1 1 Reserved Bit 4 PS based SMS Support (PSSS)0 MS does not support PS based SMS 1 MS supports PS based SMS

As illustrated in Tables 7 and 8, Bit 4 in octet 1 can be a PS based SMSSupport (PSSS) message in the UE EPS Attach Type IE. In this example, aBit value of 0 provides the message that the MS does not support PSbased SMS. A Bit value of 1 provides the message that the MS supports PSbased SMS and does CS registration only to receive SMS service via theCS domain. The IE illustrated in Table 7 and 8 can be included in theAttach Request message shown in FIG. 3.

Solution E

In this solution, an existing IE MS Network Capability in the ATTACHREQUEST message can be extended to indicate a UE PS-only capability tothe network; i.e. UE's intent to request CS registration only forobtaining SMS based service, but is capable of PS based SMS.

In accordance with one embodiment, the MS Network Capability IE, whichis defined in section 10.5.5.12 of 3GPP TS 24.008, can be configured toinclude a PS based SMS Support message, as follows

TABLE 9 MS Network Capability information element . . . PS based SMSSupport (PSSS) 0 MS does not support PS based SMS 1 MS supports PS basedSMS

As illustrated in Table 9, a selected bit in a selected octet of the IEcan be a PS based SMS Support (PSSS) message. In this example, a Bitvalue of 0 provides the message that the MS does not support PS basedSMS. A Bit value of 1 provides the message that the MS supports PS basedSMS and does CS registration only to receive SMS service via the CSdomain. The IE illustrated in Table 9 can be included in the AttachRequest message shown in FIG. 3.

While several examples have been provided to illustrate communicationfrom the UE to the 3GPP network to communicate the UE's ability toperform PS based SMS support via the Attach Request message, this is notintended to be limiting. There are also additional ways in which thisinformation could be communicated.

For example, enhancements, substantially similar to those shown inSolutions A-E, can be made to the Tracking Area Update Request Messagedescribed in section 8.2.29 of 3GPP TS 24.301. These enhancements can beused to communicate the UE's ability to perform PS based SMS support viathe Tracking Area Update Request Message, as can be appreciated.

3GPP Network Messaging

In order for the 3GPP wireless network to support PS based SMS support,the network can support SMS communication over the Non Access Stratum(NAS) layer. The network can provide an indication to a UE if SMS overNAS is supported by the MME.

In addition, in a GSM network, when an MS is switched on, theInternational Mobile Subscriber Identity (IMSI) attach procedure isexecuted. This procedure is used to connect the MS with the MobileSwitching Center (MSC) and Visitor Location Register (VLR) to registerthe MS in the network. With the ability to perform PS based SMS support,an MS/UE may no longer need to connect with the MSC. Accordingly, anIMSI attach procedure is not needed. When the network is informed that aUE supports PS based SMS support, the network can then reject any IMSIattach request. The network can send an indication to the UE that theIMSI attach was rejected due to the PS-only service provisioning basedon the UE capability and therefore, the UE shall not imitate any CSrelated procedures.

To accomplish this, an EPS network feature supported IE in the AttachAccept message defined in the 3GPP TS 24.301 specification can beenhanced to include additional information. Two different examples,referred to as Solution A and Solution B, are provided in the proceedingparagraphs. These examples are not intended to be limiting. A variety ofmessaging means may be used to allow the 3GPP network to communicatewith the UE to identify the network's ability to perform PS based SMSsupport.

Solution A

In this solution, if an MME in an EPS supports SMS over NAS then it canindicate the support to the UE in the Attach Accept message using a newEPS Network Feature Supported IE. One example format of the new IE inthe Attach Accept message is provided below.

The purpose of the EPS Network Feature Support IE is to indicate whethercertain features are supported by the network. The EPS Network FeatureSupport IE can be coded as shown in Tables 10 and 11. In one example,the EPS Network Feature Support IE is a type 4 IE with a length of 3octets.

TABLE 10 EPS Network Feature Support information element

TABLE 11 EPS Network Feature Support information element . . . Bit 7 0SMS over NAS not supported 1 SMS over NAS is supported Bit 8 of octet 3is spare and shall be coded all zero.

As illustrated in Tables 10 and 11, Bit 7 in octet 3 can be a PS basedSMS Support (PSSS) message in the EPS Network Support IE. In thisexample, a Bit value of 0 provides the message that the SMS over NAS isnot supported. A Bit value of 1 provides the message that SMS over NASis supported by the EPS. The IE illustrated in Table 10 and 11 can beincluded in the Attach Accept message communicated from the EPS to theUE.

Solution B

In this solution, if an MME in an EPS supports SMS over NAS then it canindicate the support to the UE in the Attach Accept message using a newEPS Extended Network Feature Supported IE. One example format of the newIE in the Attach Accept message is provided below.

The EPS Extended Network Feature Support IE is to indicate whethercertain features are supported by the network. The EPS Extended NetworkFeature Support IE can be coded as shown in Tables 12 and 13.

TABLE 12 EPS Extended Network Feature Support information element

TABLE 13 EPS Extended Network Feature Support information element PSbased SMS Support (PSSS) (octet 1) Bit 1 0 SMS over NAS not supported 1SMS over NAS supported Bit 1 set to 1 indicates SMS over NAS issupported by SGSN Bits 4 to 2 of octet 1 are spare and shall be allcoded as zero.

As illustrated in Tables 12 and 13, Bit 1 in octet 1 can be a PS basedSMS Support (PSSS) message in the EPS Extended Network Support IE. Inthis example, a Bit value of 0 provides the message that the SMS overNAS is not supported by the EPS. A Bit value of 1 provides the messagethat SMS over NAS is supported by the EPS. The IE illustrated in Table12 and 13 can be included in the Attach Accept message communicated fromthe EPS to the UE.

While several examples have been provided to illustrate communicationfrom the EPS to the UE to communicate the network's ability to performPS based SMS support via the Attach Accept message, this is not intendedto be limiting. There are also additional ways in which this informationcould be communicated.

For example, enhancements, substantially similar to those shown inSolutions A-B, can be made to the Tracking Area Update Accept Messagedescribed in section 8.2.26 of 3GPP TS 24.301. These enhancements can beused to communicate the network's ability to perform SMS over NAS t viathe Tracking Area Update Accept Message, as can be appreciated.

EMM Cause Value

In addition to the PSSS message from the EPS to the UE, an EPS mobilitymanagement (EMM) message can be communicated from the EPS to the UE. TheEMM message may be communicated in an IE. The purpose of the EMM causeIE is to indicate the reason why an EMM request from the UE Is rejectedby the network. In this case, the EMM cause IE can be used to identifythat an international mobile subscriber identity (IMSI) attach isrejected as PS only is supported and the EPS network supports SMS overthe NAS. Accordingly, no IMSI attach is necessary, as previouslydiscussed. The EMM cause IE is a type 3 IE with 2 octets length. Oneexample is shown in Table 14 and in FIG. 4.

TABLE 14 EMM cause information element

As shown in FIG. 4, Cause #41 can provide information that the IMSIattach is rejected by the EPS since PS-only is supported and the networksupports SMS over NAS. This EMM cause can be sent to the UE when the UEis supposed to send and receive SMS via PS NAS signaling.

In another example embodiment, a method 500 for communicating a shortmessage service (SMS) communications in a packet switched (PS) domain ofan evolved packet system (EPS) network is disclosed, as depicted in theflow chart of FIG. 5. The method comprises receiving, at a core network(CN) control node, a request message from a user equipment (UE)indicating that the UE supports PS based SMS and performs a circuitswitched (CS) registration only to receive SMS service via a CS domain,as shown in block 510; and sending, from the CN control node, an acceptmessage to the UE indicating that SMS over a non-access stratum (NAS) issupported by the CN control node, as shown in block 520. The CN controlnode can be one of a mobility management entity (MME) and a servinggeneral packet radio service (GPRS) support node (SGSN), as previouslydiscussed.

In one embodiment, the CN control node of the method 500 can be either amobility management entity (MME) or a serving general packet radioservice (GPRS) support node (SGSN). The request message can be either anattach request message or a tracking area update request message. Theaccept message can be either an attach accept message or a tracking areaupdate accept message. The attach accept message or the tracking areaupdate accept message can indicate that the IMSI attach is only for SMS.

The method 500 can further comprise sending, from the CN control node,an evolved packet system (EPS) mobility management (EMM) messageidentifying that an international mobile subscriber identity (IMSI)attach is rejected as PS only is supported and the EPS network supportsSMS over the NAS.

The method 500 can further comprise receiving an attach request messageor a tracking area update request message, wherein the attach requestmessage or the tracking area update request message comprises anadditional update type information element (IE) having a selected bitset to indicate if the UE supports PS based SMS and performs the CSregistration only to receive SMS service via the CS domain.

The method 500 can further comprise receiving an attach request messageor a tracking area update request message, wherein the attach requestmessage or the tracking area update request message comprises a mobilestation network feature support information element (IE) having aselected bit set to indicate if the UE supports PS based SMS andperforms the CS registration only to receive SMS service via the CSdomain.

The method 500 can further comprise receiving an attach request messageor a tracking area update request message, wherein the attach requestmessage or the tracking area update request message comprises a UEnetwork capability information element (IE) having a selected bit set toindicate if the UE supports PS based SMS and performs the CSregistration only to receive SMS service via the CS domain.

The method 500 can further comprise receiving an attach request messageor a tracking area update request message, wherein the attach requestmessage or the tracking area update request message comprises an EPSattach type information element (IE) having a selected bit set toindicate if the UE supports PS based SMS and performs the CSregistration only to receive SMS service via the CS domain.

The method 500 can further comprise receiving an attach request messageor a tracking area update request message, wherein the attach requestmessage or the tracking area update request message comprises a mobilestation network capability information element (IE) having a selectedbit set to indicate if the UE supports PS based SMS and performs the CSregistration only to receive SMS service via the CS domain.

The method 500 can further comprise sending an attach accept message ora tracking area update accept message to the UE, wherein the attachaccept message or the tracking area update accept message comprises anEPS network feature support information element (IE) using a selectedbit in the IE to identify if SMS over NAS is supported or is notsupported by the EPS network.

The method 500 can further comprise sending an attach accept message ora tracking area update accept message to the UE, wherein the attachaccept message or the tracking area update accept message comprises anEPS extended network feature support information element (IE) using aselected bit in the IE to identify if SMS over NAS is supported or isnot supported by the EPS network.

In one embodiment, the method 500 comprises providing a non-broadcastedLocation Area Identity (LAI) by the CN control node. A reservedTemporary Mobile Subscriber Identity (TMSI) from the CN control node canbe provided to the UE.

The method 500 can further comprise sending a notification from the CNcontrol node to a Home Subscriber Server that the CN control node iscapable of SMS transfer without establishing an SGs association with amobile switching center (MSC).

In another embodiment, a method 600 for adapting a wireless network forpacket switched communication of a short message service message isdescribed, as depicted in the flow chart of FIG. 6. The method comprisestransmitting a request message from a user equipment (UE) to a mobilitymanagement entity (MME) indicating that the UE supports packet switched(PS) based short message service (SMS) and performs a circuit switched(CS) registration only to receive CS based SMS service, as shown inblock 610; and receiving, at the UE, an accept message from the MMEindicating that SMS over a non-access stratum (NAS) is supported by theMME, as shown in block 620. In one embodiment, the request message canbe one of an attach request message and a tracking area update requestmessage. The accept message can be one of an attach accept message and atracking area update accept message, as previously discussed.

The method 600 can further comprise sending, from MME, an evolved packetsystem (EPS) mobility management (EMM) message identifying a cause codethat an international mobile subscriber identity (IMSI) attach isrejected as PS only is supported and the EPS network supports SMS overthe NAS. The operation of transmitting the request message can furthercomprise transmitting an attach request message or a tracking areaupdate request message, wherein the attach request message or thetracking area update request message comprises an additional update typeinformation element (IE) having a selected bit set to indicate if the UEsupports PS based SMS and performs the CS registration only to receiveSMS service via the CS domain.

In another embodiment, a mobility management entity (MME) configured toadapt a user equipment (UE) for packet switched (PS) communication of ashort message service (SMS) message is disclosed. The MME comprises a PSsupport module operable at the MME, as illustrated in FIG. 2. The PSsupport module is configured to receive a request message from a UEindicating that the UE supports PS based SMS and performs a circuitswitched (CS) registration only to receive SMS service via a CS domain;and send an accept message to the UE indicating that SMS over anon-access stratum (NAS) is supported by MME. The request message can beone of an attach request message and a tracking area update requestmessage. The accept message can be one of an attach accept message and atracking area update accept message.

In one embodiment, the PS support module is further configured totransmit an evolved packet system (EPS) mobility management (EMM)message identifying a cause code that an international mobile subscriberidentity (IMSI) attach is rejected as PS only is supported and the EPSnetwork supports SMS over the NAS.

In another embodiment, the PS support module is further configured toreceive the request message from the UE, wherein receiving the requestmessage further comprises receiving an attach request message or atracking area update request message, wherein the attach request messageor the tracking area update request message comprises an additionalupdate type information element (IE) having a selected bit set toindicate if the UE supports PS based SMS and performs the CSregistration only to receive SMS service via the CS domain.

FIG. 7 provides an example illustration of a mobile device, such as auser equipment (UE), a mobile station (MS), a mobile wireless device, amobile communication device, a tablet, a handset, or other type ofmobile wireless device. The mobile device can include one or moreantennas configured to communicate with a base station (BS), an evolvedNode B (eNB), or other type of wireless wide area network (WWAN) accesspoint. The mobile device can be configured to communicate using at leastone wireless communication standard including 3GPP LTE, WiMAX, HighSpeed Packet Access (HSPA), Bluetooth, and WiFi. The mobile device cancommunicate using separate antennas for each wireless communicationstandard or shared antennas for multiple wireless communicationstandards. The mobile device can communicate in a wireless local areanetwork (WLAN), a wireless personal area network (WPAN), and/or awireless wide area network (WWAN).

FIG. 7 also provides an illustration of a microphone and one or morespeakers that can be used for audio input and output from the mobiledevice. The display screen may be a liquid crystal display (LCD) screen,or other type of display screen such as an organic light emitting diode(OLED) display. The display screen can be configured as a touch screen.The touch screen may use capacitive, resistive, or another type of touchscreen technology. An application processor and a graphics processor canbe coupled to internal memory to provide processing and displaycapabilities. A non-volatile memory port can also be used to providedata input/output options to a user. The non-volatile memory port mayalso be used to expand the memory capabilities of the mobile device. Akeyboard may be integrated with the mobile device or wirelesslyconnected to the mobile device to provide additional user input. Avirtual keyboard may also be provided using the touch screen.

It should be understood that many of the functional units described inthis specification have been labeled as modules, in order to moreparticularly emphasize their implementation independence. For example, amodule may be implemented as a hardware circuit comprising custom VLSIcircuits or gate arrays, off-the-shelf semiconductors such as logicchips, transistors, or other discrete components. A module may also beimplemented in programmable hardware devices such as field programmablegate arrays, programmable array logic, programmable logic devices or thelike.

Modules may also be implemented in software for execution by varioustypes of processors. An identified module of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object,procedure, or function. Nevertheless, the executables of an identifiedmodule need not be physically located together, but may comprisedisparate instructions stored in different locations which, when joinedlogically together, comprise the module and achieve the stated purposefor the module.

Indeed, a module of executable code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different storage devices, and may exist, atleast partially, merely as electronic signals on a system or network.The modules may be passive or active, including agents operable toperform desired functions.

Various techniques, or certain aspects or portions thereof, may take theform of program code (i.e., instructions) embodied in tangible media,such as floppy diskettes, CD-ROMs, hard drives, or any othermachine-readable storage medium wherein, when the program code is loadedinto and executed by a machine, such as a computer, the machine becomesan apparatus for practicing the various techniques. In the case ofprogram code execution on programmable computers, the computing devicemay include a processor, a storage medium readable by the processor(including volatile and non-volatile memory and/or storage elements), atleast one input device, and at least one output device. One or moreprograms that may implement or utilize the various techniques describedherein may use an application programming interface (API), reusablecontrols, and the like. Such programs may be implemented in a high levelprocedural or object oriented programming language to communicate with acomputer system. However, the program(s) may be implemented in assemblyor machine language, if desired. In any case, the language may be acompiled or interpreted language, and combined with hardwareimplementations.

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present invention. Thus, appearancesof the phrases “in one embodiment” or “in an embodiment” in variousplaces throughout this specification are not necessarily all referringto the same embodiment.

As used herein, a plurality of items, structural elements, compositionalelements, and/or materials may be presented in a common list forconvenience. However, these lists should be construed as though eachmember of the list is individually identified as a separate and uniquemember. Thus, no individual member of such list should be construed as ade facto equivalent of any other member of the same list solely based ontheir presentation in a common group without indications to thecontrary. In addition, various embodiments and example of the presentinvention may be referred to herein along with alternatives for thevarious components thereof. It is understood that such embodiments,examples, and alternatives are not to be construed as defactoequivalents of one another, but are to be considered as separate andautonomous representations of the present invention.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of materials, fasteners, sizes, lengths, widths, shapes, etc.,to provide a thorough understanding of embodiments of the invention. Oneskilled in the relevant art will recognize, however, that the inventioncan be practiced without one or more of the specific details, or withother methods, components, materials, etc. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring aspects of the invention.

While the forgoing examples are illustrative of the principles of thepresent invention in one or more particular applications, it will beapparent to those of ordinary skill in the art that numerousmodifications in form, usage and details of implementation can be madewithout the exercise of inventive faculty, and without departing fromthe principles and concepts of the invention. Accordingly, it is notintended that the invention be limited, except as by the claims setforth below.

What is claimed is:
 1. A method for communicating a short messageservice (SMS) communications in a packet switched (PS) domain of anevolved packet system (EPS) network, comprising: receiving, at a corenetwork (CN) control node, a request message from a user equipment (UE)indicating that the UE supports PS based SMS and performs a circuitswitched (CS) registration only to receive SMS service via a CS domain;and sending, from the CN control node, an accept message to the UEindicating that SMS over a non-access stratum (NAS) is supported by theCN control node.
 2. The method of claim 1, wherein the CN control nodeis one of a mobility management entity (MME) and a serving generalpacket radio service (GPRS) support node (SGSN).
 3. The method of claim1, wherein the request message is one of an attach request message and atracking area update request message.
 4. The method of claim 1, whereinthe accept message is one of an attach accept message and a trackingarea update accept message.
 5. The method of claim 1, further comprisingsending, from the CN control node, an evolved packet system (EPS)mobility management (EMM) message identifying that an internationalmobile subscriber identity (IMSI) attach is rejected as PS only issupported and the EPS network supports SMS over the NAS.
 6. The methodof claim 4, further comprising indicating in the attach accept messageor the tracking area update accept message that the IMSI attach is onlyfor SMS.
 7. The method of claim 1, wherein receiving the request messagefurther comprises receiving an attach request message or a tracking areaupdate request message, wherein the attach request message or thetracking area update request message comprises an additional update typeinformation element (IE) having a selected bit set to indicate if the UEsupports PS based SMS and performs the CS registration only to receiveSMS service via the CS domain.
 8. The method of claim 1, whereinreceiving the request message further comprises receiving an attachrequest message or a tracking area update request message, wherein theattach request message or the tracking area update request messagecomprises a mobile station network feature support information element(IE) having a selected bit set to indicate if the UE supports PS basedSMS and performs the CS registration only to receive SMS service via theCS domain.
 9. The method of claim 1, wherein receiving the requestmessage further comprises receiving an attach request message or atracking area update request message, wherein the attach request messageor the tracking area update request message comprises a UE networkcapability information element (IE) having a selected bit set toindicate if the UE supports PS based SMS and performs the CSregistration only to receive SMS service via the CS domain.
 10. Themethod of claim 1, wherein receiving the request message furthercomprises receiving an attach request message or a tracking area updaterequest message, wherein the attach request message or the tracking areaupdate request message comprises an EPS attach type information element(IE) having a selected bit set to indicate if the UE supports PS basedSMS and performs the CS registration only to receive SMS service via theCS domain.
 11. The method of claim 1, wherein receiving the requestmessage further comprises receiving an attach request message or atracking area update request message, wherein the attach request messageor the tracking area update request message comprises a mobile stationnetwork capability information element (IE) having a selected bit set toindicate if the UE supports PS based SMS and performs the CSregistration only to receive SMS service via the CS domain.
 12. Themethod of claim 1, wherein sending the accept message further comprisessending an attach accept message or a tracking area update acceptmessage to the UE, wherein the attach accept message or the trackingarea update accept message comprises an EPS network feature supportinformation element (IE) using a selected bit in the IE to identify ifSMS over NAS is supported or is not supported by the EPS network. 13.The method of claim 1, wherein sending the accept message furthercomprises sending an attach accept message or a tracking area updateaccept message to the UE, wherein the attach accept message or thetracking area update accept message comprises an EPS extended networkfeature support information element (IE) using a selected bit in the IEto identify if SMS over NAS is supported or is not supported by the EPSnetwork.
 14. The method of claim 1, further comprising providing anon-broadcasted Location Area Identity (LAI) by the CN control node. 15.The method of claim 1, further comprising providing a reserved TemporaryMobile Subscriber Identity (TMSI) from the CN control node to the UE.16. The method of claim 1, further comprising sending a notificationfrom the CN control node to a Home Subscriber Server that the CN controlnode is capable of SMS transfer without establishing an SGs associationwith a mobile switching center (MSC).
 17. A non-transitory machinereadable storage medium comprising a plurality of instructions adaptedto be executed to implement the method for adapting a wireless networkfor packet switched communication of a short message service message,comprising: transmitting a request message from a user equipment (UE) toa mobility management entity (MME) indicating that the UE supportspacket switched (PS) based short message service (SMS) and performs acircuit switched (CS) registration only to receive CS based SMS service;receiving, at the UE, an accept message from the MME indicating that SMSover a non-access stratum (NAS) is supported by the MME.
 18. Thenon-transitory machine readable storage medium of claim 17, furthercomprising transmitting the request message, wherein the request messageis one of an attach request message and a tracking area update requestmessage.
 19. The non-transitory machine readable storage medium of claim17, further comprising sending, from MME, an evolved packet system (EPS)mobility management (EMM) message identifying a cause code that aninternational mobile subscriber identity (IMSI) attach is rejected as PSonly is supported and the EPS network supports SMS over the NAS.
 20. Thenon-transitory machine readable storage medium of claim 17, whereintransmitting the request message further comprises transmitting anattach request message or a tracking area update request message,wherein the attach request message or the tracking area update requestmessage comprises an additional update type information element (IE)having a selected bit set to indicate if the UE supports PS based SMSand performs the CS registration only to receive SMS service via the CSdomain.
 21. A mobility management entity (MME) configured to adapt auser equipment (UE) for packet switched (PS) communication of a shortmessage service (SMS) message, comprising: a PS support module operableat the MME and configured to: receive a request message from a UEindicating that the UE supports PS based SMS and performs a circuitswitched (CS) registration only to receive SMS service via a CS domain;and send an accept message to the UE indicating that SMS over anon-access stratum (NAS) is supported by MME.
 22. The MME of claim 21,wherein the PS support module is further configured to transmit anevolved packet system (EPS) mobility management (EMM) messageidentifying a cause code that an international mobile subscriberidentity (IMSI) attach is rejected as PS only is supported and the EPSnetwork supports SMS over the NAS.
 23. The MME of claim 21, furthercomprising receiving the request message from the UE, wherein receivingthe request message further comprises receiving an attach requestmessage or a tracking area update request message, wherein the attachrequest message or the tracking area update request message comprises anadditional update type information element (IE) having a selected bitset to indicate if the UE supports PS based SMS and performs the CSregistration only to receive SMS service via the CS domain.
 24. The MMEof claim 21, wherein the request message is one of an attach requestmessage and a tracking area update request message.
 25. The MME of claim21, wherein the accept message is one of an attach accept message and atracking area update accept message.